Akita T
Caldari Navy Volunteer Task Force
   |
Posted - 2007.12.07 21:03:00 -
[1]
First and foremost, the Trinity release was RUSHED.
Now, you can debate as much as you want for or against it being a good thing (shiny stuff sooner, or shiny stuff stable and properly tested), but this one thing is not debatable, it was rushed heavily.
Not only that, but the LAST SiSi build ran quite differently from the current TQ build, which raises the question wether the current build was tested AT ALL on a less-than-just-internal scale.
The Bootini Incident, for how high-profile it still is, was a MINOR faux-pas, on the grand scale of things.
I mean, seriously, it only affected Windows XP (or earlier) that had EVE installed on the same partition as the OS.
Not only that, but it is easily fixable.
The Jumpclone Bug should have been noticed by QA if it would have been on the test list.
Suspect it wasn't even on the test list at all. Proper regression testing my ass.
Reimbursements SHOULD cover this issue, to a degree, but nevertheless, there's lost SP due to lack of implants... not extremely nasty yet, but the manner of refunding them could cause an even greater issue if "done wrong".
Also, the lack of an easily accessible/visible official statement about the issue is not very encouraging.
The "sov. and POS stuff" should have been noticed by QA as well.
I mean, come ON, it's like nobody even TRIED it at all on the final build, seriously.
This is the most damaging and far-reaching screw-up in the entire patch radioactive fallout.
THIS ALONE should probably warrant a rollback, or at least some serious reimbursements... but it's a bit late for that.
Either way, again, the lack of an EASILY VISIBLE clear-and-to-the-point announcement about it is appaling.
___
Don't get me wrong, for the AMOUNT of workload needed for this patch, and considering the RELEASE DATE, it went out pretty well.
What I am questioning here is the decision to roll out Trinity without proper and thorough testing (it's pretty damned obvious) to meet some deadline that wasn't even announced a long time before.
And since the things came out the way they did come out... and, well, not much CAN be done now...
How about a short devblog/announcement regarding the "deployment status" on one hand, and "damage control" planned measures on the other ?
If nothing else, then at least that.
1|2|3|4|5. |